Systems and methods for enhanced autonegotiation

ABSTRACT

An improved autonegotiation approach includes determining that a negotiated rate between a first network device and a second network device exceeds data transfer capacity over a network path downstream of the second network device. In response, a configuration message is generated and transmitted to the first network device. When received by the first network device, the configuration message causes the first network device to limit data transfer between the first network device and the second network device to no more than the downstream data transfer capacity.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is related to and claims priority under 35 U.S.C. §119(e) from U.S. Patent Application No. 62/533,924, filed Jul. 18, 2017entitled “SYSTEMS AND METHODS FOR ENHANCED AUTONEGOTIATION,” the entirecontents of which is incorporated herein by reference for all purposes.

TECHNICAL FIELD

Aspects of the present disclosure involve negotiating transmissionparameters for transmitting data between network devices. Morespecifically, aspects of the present disclosure involve dynamicmodification of data transfer rate limits between network devices toaccount for potential bottlenecks and other transfer rate reductionsalong paths extending from the network devices.

BACKGROUND

Autonegotiation generally refers to the process by which two networkeddevices determine a set of parameters by which data is to be exchangedbetween the devices. Such parameters may include, without limitation,one or more rates of transmission, a duplex mode, and/or flow controlmechanisms. During autonegotiation, the connected devices share theircapabilities regarding the transmission parameters and then choose thehighest performance transmission mode supported by both devices.

Although the autonegotiation process may select transmission parametersthat are supported by two devices, the same parameters may beincompatible with networks to which the devices are coupled. Forexample, one of the network devices may be a transceiver adapted toconvert network traffic from a first network protocol to a secondnetwork protocol, the second network protocol having transmissionparameters, such as bandwidth, that are incompatible or that do notmatch with those of the first network. The resulting mismatch may resultin lost data and/or inefficient network performance.

It is with these observations in mind, among others, that aspects of thepresent disclosure were conceived.

SUMMARY

In one implementation of the present disclosure, a method forestablishing a data transfer rate between network endpoints is provided.The method includes initiating a connection between a first endpoint ofa first network and a second endpoint of a second network, theconnection between the endpoint of the first network and the endpoint ofthe second network supporting data transfer at up to a first transferrate. The method next includes determining the first transfer rate isgreater than a second transfer rate for transferring data over thesecond network. In response to doing so, a configuration message istransmitted to a network device corresponding to the first endpoint. Theconfiguration message causes the network device to limit transfer ofdata over the connection from the first endpoint to the second endpointto no greater than the second transfer rate.

In another implementation of the present disclosure, a system forcontrolling data transfer rates between network devices is provided. Thesystem includes a computing device comprising a processor and one ormore non-transitory tangible computer-readable storage media storingcomputer-executable instructions. When executed by the processor, theinstructions cause the computing device to determine that a negotiatedtransfer rate for transferring data from a first network device to asecond network device over a first network exceeds a downstream transferrate, the downstream transfer rate corresponding to a transfer ratebetween the second network device and a third network device over asecond network. In response to making such a determination, theinstructions further cause the computing device to generate aconfiguration message that, when received by the first network device,causes the first network device to limit data transfer between the firstnetwork device and the second network device to no greater than thedownstream transfer rate. The instructions also cause the computingdevice to transmit the configuration message to the first networkdevice.

In yet another implementation of the present disclosure, anon-transitory computer readable medium is provided. The computerreadable medium includes instructions that, when executed by one or moreprocessors of a computing device, cause the computing device to todetermine that a negotiated transfer rate for transferring data from afirst network device to a second network device over a first networkexceeds a downstream transfer rate, the downstream transfer ratecorresponding to a transfer rate between the second network device and athird network device over a second network. In response to making such adetermination, the instructions further cause the computing device togenerate a configuration message that, when received by the firstnetwork device, causes the first network device to limit data transferbetween the first network device and the second network device to nogreater than the downstream transfer rate. The instructions also causethe computing device to transmit the configuration message to the firstnetwork device.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing and other objects, features, and advantages of the presentdisclosure set forth herein will be apparent from the followingdescription of particular embodiments of those inventive concepts, asillustrated in the accompanying drawings. It should be noted that thedrawings are not necessarily to scale; however, the emphasis instead isbeing placed on illustrating the principles of the inventive concepts.Also, in the drawings the like reference characters may refer to thesame parts or similar throughout the different views. It is intendedthat the embodiments and figures disclosed herein are to be consideredillustrative rather than limiting.

FIG. 1 is a schematic illustration of an example network environment fortransferring data between networks.

FIG. 2 is a schematic illustration of as second example networkenvironment for transferring data between networks.

FIG. 3 is a flow chart illustrating an example method for negotiatingdata transfer rates between network devices.

FIG. 4 is an example computing system that may implement various systemsand methods of the presently disclosed technology.

DETAILED DESCRIPTION

Conventional autonegotiation enables data transmission between devicesat the highest common rate supported by each device. Autonegotiationgenerally includes an exchange of messages in which each device declaresthe different transmission parameters under which it may operate. Suchparameters may include, without limitation, transmission rates andwhether full or half duplex transmission is supported. Autonegotiationresides in the physical layer and, as a result, the transmissionparameters exchanged by a device are dictated by the physicalcapabilities of the device and often by standards associated with thenetwork protocol for which the device is designed. For example, Ethernetdevices generally support transmission at rates corresponding to powersof ten megabits (Mbit) per second (e.g., 1 Mbit/s, 10 Mbit/s, 100Mbit/s, 1000 Mbit/s (i.e., 1 gigabit (Gbit) per second), etc.), each ofwhich may be supported in either full or half duplex mode. Afterexchanging transmission parameters, each device within the exchangeidentifies a common set of transmission parameters for use in subsequentdata transmission. In certain implementations, the process ofidentifying a common set of transmission parameters prioritizes hightransfer rates over full duplex transmission and full duplextransmission over half duplex transmission. Accordingly, devicesgenerally select the highest available common transfer rate and fullduplex communication, if available.

When devices operating using the same protocol undergo autonegotiation,the list of exchanged data transmission parameters are similar and ofteninclude one or more matches. For example, the transmission parametersexchanged between two Ethernet-enabled devices will often include atleast some common transmission rates even though one of the devices mayalso support faster rates. However, problems may arise when one of thenetwork devices is used to exchange data between networks havingdifferent protocols and different transmission parameters. SONETnetworks, for example, commonly operate using Synchronous TransportSignal 1 (STS-1) or Synchronous Transport Signal 3 (STS-3c) framingcarried over links that support transmission rates at approximately 50Mbit/s, and approximately 150 Mbit/s, respectively. Differenttransmission rates are generally attained by the virtual concatenationof multiple STS-1, STS-3c, STS-12c, STS-24c, and STS-48c channels, amongothers, but are generally limited to multiples of the base STS-1,STS-3c, STS-12c, etc. transmission rates. Nevertheless, for a wide rangeof transmission rates, services provisioned over a SONET network may beprovided with greater granularity than is supported by Ethernet andtransmission rate mismatches between the capacity of the SONET networkand any Ethernet networks connected thereto.

For example, the nearest Ethernet transfer rates for providing data to aSONET link provisioned for a 600 Mbit/s service are 100 Mbit/s and 1Gbit/s. If a 100 Mbit/s transfer rate is used to transfer data betweenan endpoint device of the Ethernet network and a corresponding endpointdevice of the SONET network, 500 Mbit/s of bandwidth goes unused. On theother hand, the 1 Gbit/s transfer rate exceeds the provisioned servicerate by 400 Mbit/s. In certain conventional applications, the excessdata is simply ignored (e.g., by sending the corresponding excess signalenergy to ground), which can render the data stream largely useless. Inother conventional applications, an endpoint device of the Ethernetnetwork may be manually configured to include a buffer that accepts 1Gbit every two seconds such that 600 Mbit may be transmitted during thefirst second and 400 Gbit may be transmitted during the subsequentsecond. Although the data is fully transmitted, the result is an averagetransmission rate (i.e., 500 Mbit/s) from the Ethernet network to theSONET network that is below the provisioned rate of the 600 Mbit/sservice.

Considering the foregoing challenges, systems and methods disclosedherein are directed to implementing an improved autonegotiation processfor use in facilitating data transmission between disparate networks. Inone example, the process includes determining a first transfer ratebetween a first endpoint device of a first network and a second endpointdevice of a second network. The first transfer rate may correspond witha maximum transfer rate between the endpoint devices. If the transferrate exceeds a second transfer rate, which may correspond to a maximumtransfer rate over the second network, a configuration message is sentto the first endpoint device that limits data transfer from the firstendpoint device to the second endpoint device to the second rate.

With reference to the previous example, the first endpoint device may bea router, switch or similar device coupled to the Ethernet network, andthe second endpoint device may be an Ethernet transceiver adapted toconvert Ethernet traffic to SONET traffic. During the autonegotiationprocess, the transceiver and the router exchange transmission parametersand determine that transmission between the two devices may occur at upto 1 Gbit/s (i.e., the first transfer rate) based on the correspondingphysical layer of each endpoint device. The second transfer rate, whichcorresponds to a transfer rate over the second network, may then beidentified as 600M bit/s. The second transfer rate may correspond toseveral data rates including, without limitation, a maximum data rateprovisioned by a customer associated with the first network, a physicallimitation of the SONET network link, and a maximum transfer rate of adestination endpoint device. Upon determining that the second transferrate is below the first transfer rate, a configuration message is sentto the first endpoint device that causes the first endpoint device toautomatically limit traffic sent to the second endpoint device to thesecond transfer rate.

As previously noted, the second transfer rate may correspond to varioustransfer rates related to data transmission over the second network.Accordingly, systems in accordance with this disclosure may be adaptedto determine the second transfer rate in various ways. For example, incertain implementations, the second data rate may be preprogrammed orotherwise stored in memory of the second endpoint device. In otherimplementations, a computing device in communication with the secondendpoint device may receive notification of the negotiation processbetween the first and second endpoint devices and may perform a lookupor other function on a table including a list of services or datatransfer rates. The computing device may be further adapted to generateand send the configuration message to the first endpoint device. Instill other implementations, the second transfer rate may correspond toa negotiated transfer rate between another endpoint device of the secondnetwork and another external device. The second transfer rate may alsodynamically change to reflect conditions of the second network andcorresponding configuration messages may be transmitted to the firstendpoint device when such changed conditions occur. For example, thesecond transfer rate may be updated when channel capacity of the secondnetwork is impaired or otherwise encounters an error and a correspondingconfiguration message may be automatically generated and transmitted tothe first endpoint device when such an error occurs.

Although primarily described in the context of communication between anEthernet network and a SONET network, the systems and methods describedherein may be applied to any network devices that may connect networksor subnetworks with different transmission parameters. Accordingly, tothe extent examples disclosed herein refer to Ethernet or SONET endpointdevices, such distinctions are used simply to provide context andclarity to the examples. Moreover, to the extent the disclosure refersto communication between endpoint devices, such endpoint devices are notnecessarily separate devices but, rather, may be separate components ormodules integrated into a single device. For example, a router or switchmay be integrated into a single device with a transceiver thatfacilitates communication between different networks.

FIG. 1 is a schematic illustration of an example network environment 100for transferring data between networks. The implementation of FIG. 1illustrates transmission of data from a first Ethernet network 102 to asecond Ethernet network 106 via a SON ET network 104. Transmission ofdata between the networks is facilitated by endpoint devices adapted toprocess and route incoming data. For example, the first Ethernet network102 includes a first Ethernet endpoint device 108 communicativelycoupled to a first SONET endpoint device 110 by a first link 109 tofacilitate data transmission between the first Ethernet network 102 andthe SONET network 104. The first SONET endpoint device 110 is in turncommunicatively coupled to the SONET network 104 by one or more firstSONET channels 111. Similarly, a second SONET endpoint device 112 iscommunicatively coupled to a second Ethernet endpoint device 114 by asecond link 113 to facilitate data transmission between the SONETnetwork 104 and the second Ethernet network 106. The second SONETendpoint device 112 is also coupled to the SONET network 104 by one ormore second SONET channels 115. Accordingly, data originating fromeither the first or second Ethernet network 102, 106 and destined forthe second and first Ethernet network 106, 102, respectively, passesthrough each of the endpoint devices.

The interconnected components of the network environment 100 may undergoan autonegotiation process in which transfer rates between devices areestablished. For example, upon connection and startup of the firstEthernet endpoint device 108 and the first SONET endpoint device 110,the endpoint devices 108, 110 may exchange transmission parameters anddetermine a set of common transmission parameters supported by eachendpoint device 108, 110. For purposes of this disclosure, thetransmission parameters include a transmission speed, but may furtherinclude other parameters including, without limitation, whether thedevices support full or half duplex communication and specific flowcontrol parameters to be used. Generally, the autonegotiation processoccurs over the physical layer and results in selection of the highestpossible rate supported by the connected devices.

In certain instances, the endpoint devices may not support a commontransfer rate. For example, Ethernet devices generally support transferrates according to a “power of ten” model (e.g., 10 Mbit/s, 100 Mbit/s,1 Gbit/s, etc.), while the majority of SONET networks operate usinglinks that can be virtually concatenated to provide services at datatransfer rates in multiples of approximately 50, 150, or 600 Mbit/s. Asa result, a wide range of possible SONET transfer rates exist betweenthe standard Ethernet transfer rates. So, for example, a serviceprovider may provision a 600 Mbit/s SONET service. Regardless of whetherthe customer's Ethernet equipment can provide data at either 100 Mbit/sor 1 Gbit/s, autonegotiating either rate is problematic. Although theSONET service is capable of handling 100 Mbit/s, using such a rateresults in data transfer at only a fraction of the provisioned rate,which makes inefficient use of the additional dedicated SONET bandwidthpaid for by the customer. On the other hand, the provisioned SONETservice is generally unable to handle a full 1 Gbit/s. In suchinstances, many devices are configured to simply drop the excess data,resulting in an incomplete and possibly useless data stream.Alternatively, one of the endpoint devices may be manually configured tobuffer incoming data from the Ethernet network and to send the data overthe SONET network over several seconds such that the maximum provisionedrate is not exceeded. For example, in the current example, one of theendpoint devices may be configured to accept 1 Gbit/s but to transmit600 Mbit of the received data during a first second and 400 Mbit over asubsequent second. This approach still results in an overall reduceddata transfer rate (500 Mbit/s) as compared to the provisioned rate (600Mbit/s).

Referring more specifically to the network environment 100, an initialautonegotiation process between the first Ethernet endpoint device 108and the first SONET network device 110 may result in a data transferrate between the endpoint devices 108, 110 that exceeds a provisionedrate over the SONET network 104. For example, as described in thepreviously discussed example, a transfer rate of 1 Gbit/s may benegotiated between the first Ethernet endpoint device 108 and the firstSONET endpoint device 110 while a service provided over the SONETnetwork 104 may only support a transfer rate of 600 Mbit/s. Aspreviously noted, conventional SONET networks generally comprise aplurality of channels, each of which are capable of transmitting atapproximately 50, 150, or 600 Mbit/s. Accordingly, in the example ofFIG. 1, the one or more first channels 111 may correspond to four STS-3cpayloads, each of which is capable of transmitting data at approximately150 Mbit/s to achieve the provisioned 600 Mbit/s rate. To provide thefull provisioned rate, virtual concatenators may be used that act asinverse multiplexers for distributing a single stream of data overmultiple first channels. For example, data transmitted over the firstlink 109 may be passed through a virtual concatenator 116 that splitsthe data between the one or more first channels 111. Similarly, acorresponding virtual concatenator 118 may be used to convert data to orfrom the one or more second channels 115 for transmission over thesecond link 113 between the second SONET endpoint device 112 and thesecond Ethernet endpoint device 114.

Systems and methods in accordance with this disclosure address theforegoing issues by automatically determining a mismatch between thetransfer rate between endpoint devices and a transfer rate, alsoreferred to herein as a “provisioned rate”, over a network coupled toone of the endpoint devices. If such a discrepancy is present, aconfiguration message is automatically generated and sent to the higherthroughput endpoint device that causes the device to limit its transferrate to the provisioned rate. In contrast to conventionalautonegotiation, which generally occurs at the physical layer, theexchange of the configuration message(s) may occur at a higher orderlayer, such as the data link layer.

Identification of a transfer rate mismatch generally requires adetermination of the provisioned transfer rate. The process of doing somay vary depending on the specific implementation of the presentdisclosure. In one implementation, the provisioned rate may be stored inthe configuration data of an endpoint device. For example, the firstSONET endpoint device 110 may include a table or similar data structurethat includes provisioned data transfer rates for each link between thefirst SONET endpoint device 110 and other endpoint devices, such as thefirst Ethernet endpoint device 108.

In another implementation, the transfer rate over the SONET network 104may be dictated, at least in part, by a negotiated rate between otherdevices. For example, if data is being transferred from the firstEthernet network 102 to the second Ethernet network 106, a bottleneckmay occur at the second link 113 if the rate negotiated by the endpointdevices 112, 114 is less than the provisioned rate for transferring dataover the SONET network 104 or the negotiated rate over the first link109. Accordingly, part of the negotiation process may include retrievingthe transfer rate for the second link 113 from the second SONET endpointdevice 112 or a computing device with access to the configuration dataof the second SONET endpoint device 112.

In yet another implementation, a computing device 120 may becommunicatively coupled to the SONET network 104 or otherwise incommunication with the first SONET endpoint device 110. The computingdevice 120 may also be communicatively coupled to a data source 122including data corresponding to services provisioned over the SONETnetwork 104. For example, the data source 122 may include informationregarding, among other things, the provisioned transfer rates forparticular services associated with particular customers. Accordingly,during the negotiation process, the computing device 120 may receive anegotiated rate for data transfer over the first link 109 and comparethe negotiated rate with the provisioned rate for transmitting data overthe SONET network 104. Alternatively, the computing device 120 mayprovide the provisioned rate information to the first SONET endpointdevice 110 which then performs the comparison. For example, in responseto provisioning a new service, the computing device 120 may transmit amessage to the first SONET endpoint device 110 that automaticallyupdates the configuration of the first SONET endpoint device 110 toinclude the provisioned rate.

To the extent a discrepancy is identified between the transfer rate overthe first link 109 and a downstream rate (such as a provisioned rate ora lower negotiated rate between destination devices), a configurationmessage is generated and transmitted to the first Ethernet endpointdevice 108. The configuration message is adapted to automaticallyreconfigure the first Ethernet endpoint device 108 to reduce the datatransfer rate over the first link 109 to the downstream rate. Forexample, in the previously discussed example in which the first link 109is negotiated to have a rate of 1 Gbit/s but a provisioned rate over theSONET network 104 is only 600 Mbit/s, the configuration message wouldcause the first Ethernet endpoint device 108 to transmit only 600 Mbit/sover the first link 109. In certain implementations, the configurationmay be adapted to execute or modify a traffic shaping policy of thefirst Ethernet endpoint device 108. For example, if the first Ethernetendpoint device 108 is self-limiting, the configuration message mayautomatically cause the upper bound limit of the data transfer rate fromthe first Ethernet endpoint device 108 to be reduced to the downstreamrate.

The configuration message may be generated and transmitted from variouslocations within the network environment 100. In one implementation, thefirst SONET endpoint device 110 may be adapted to generate and transmitthe configuration message to the first Ethernet endpoint device 108 overthe first link 109. In another implementation, the computing device 120coupled to the SONET network 104 or a similar computing device may beadapted to generate and transmit the configuration message to the firstEthernet endpoint device 108. In such implementations, the configurationmessage may first be received by the first SONET endpoint device 110which then forwards the message to the first Ethernet endpoint device108 over the first link 109. Alternatively, the computing device 120 maybe communicatively coupled to the first Ethernet endpoint device 108over a separate connection or network such that the computing device 120may transmit the message to the first Ethernet endpoint device 108without involvement by the first SON ET endpoint device 110.

Although previously described in the context of autonegotiation duringthe initial connection between endpoint devices, the enhancedautonegotiation process described herein may also be implemented inresponse to other events. Notably, conventional autonegotiation occurson the physical layer and, as a result, generally requires a linkbetween devices to be disconnected in order to renegotiate a transferrate between the devices. In contrast, the exchange of configurationmessages within the approach disclosed herein enables dynamicmodification of transfer rates between devices without requiringtermination of existing links between the devices. Accordingly, ifavailable bandwidth is reduced, for example by one or more channels ofthe SONET network being impaired, or increased, for example by repairingsuch impaired channels, the system can automatically adjust data ratesbetween endpoint devices without downtime.

Referring to FIG. 1, one of the channels 111, 115 may become impaired oranother event may occur resulting in the channel being disabled andreducing the overall bandwidth through the SONET network 104. Inimplementations where the paths through the network 104 are composed ofSTS-1 or STS-3c channels, for example, such an error would result in areduction of approximately 50 or 150 Mbit/s, respectively. In responseto identifying such an event, a configuration message may be generatedand transmitted to the first Ethernet endpoint device 108 similarlyreducing the throughput of the first Ethernet endpoint device 108 by acommensurate amount. When the channel is restored and capacity isincreased, a second configuration message may be sent to the firstEthernet endpoint device 108 to increase throughput to the pre-erroramount.

Configuration messages may be used to change the throughput of the firstEthernet endpoint device 108 in response to modifications to an existingservice provided to a customer. More specifically, the provisioned ratefor transmitting data over the SONET network 104 may be increased ordecreased in response to customer needs. In response to such changes,corresponding configuration messages may be automatically transmitted tothe first Ethernet endpoint device 108 such that the data transfer rateover the first link 109 is similarly altered.

FIG. 2 is a schematic illustration of a second example networkenvironment 200 for transferring data between networks. Theimplementation of FIG. 2 illustrates transmission of data from a firstEthernet network 202 to each of a second Ethernet network 206 and athird Ethernet network 216 via a SONET network 204.

Transmission of data between the networks 202, 206, 216 is facilitatedby endpoint devices adapted to process and route incoming data. Forexample, the first Ethernet network 202 includes a first Ethernetendpoint device 208 communicatively coupled to a first SONET endpointdevice 210 by a first link 209 to facilitate data transmission betweenthe first Ethernet network 202 and the SONET network 204. The firstSONET endpoint device 210 is in turn communicatively coupled to theSONET network 204 by multiple sets of one or more first SONET channels211, 213. A second SON ET endpoint device 212 is communicatively coupledto a second Ethernet endpoint device 214 by a second link 215 tofacilitate data transmission between the SONET network 204 and thesecond Ethernet network 206. The second SONET endpoint device 212 isalso coupled to the SONET network 204 by one or more second SONETchannels 217. Similarly, a third SONET endpoint device 218 iscommunicatively coupled to a third Ethernet endpoint device 220 by athird link 219 to facilitate data transmission between the SONET network204 and the third Ethernet network 216. The third SONET endpoint device218 is also coupled to the SONET network 204 by one or more third SONETchannels 221.

During operation, data originating from the first Ethernet network 202may be split between the second and third Ethernet networks 206, 216.For example, the first link 209 may be divided into two separate virtualchannels 226, 228 (or similar sub-interfaces) for transmitting data toeach of the second Ethernet network 206 and the third Ethernet network216 along corresponding paths 222, 224, respectively. As illustrated inFIG. 2, the first SONET endpoint device 210 is adapted to redirect datareceived from the first Endpoint device 210 over the first virtualchannel 226 and a first set of the SONET channels 211 to the secondEthernet network 206. Similarly, the first SONET endpoint device 210 isadapted to redirect data received from the first Endpoint device 210over the second virtual channel 228 and a second set of the SONETchannels 213 to the second Ethernet network 206.

Upon connection and activation, the first Ethernet endpoint device 208and the first SONET endpoint device 210 may negotiate a first transferrate corresponding to a maximum rate over which data may be transferredover the first link 209. The bandwidth of the first link 209 is thenallocated between the first virtual channel 226 and the second virtualchannel 228 as necessary. However, each of the first path 222 and thesecond path 224 may include bottlenecks that are less than the possiblemaximum bandwidth that may be allocated to the first virtual channel 226and the second virtual channel 228, respectively. For example, the firstlink 209 may support up to 1 Gbit/s that may be distributed between thefirst virtual channel 226 and the second virtual channel 228, up to andincluding using the full 1 Gbit/s for either of the first virtualchannel 226 and the second virtual channel 228. If the first path 222includes a link over the SONET network 204 that is provisioned for lessthan 1 Gbit/s, data may be transferred over the first virtual channel226 at a rate exceeding that supported by the first path 222. As anotherexample, the third SONET endpoint device 218 and the third Ethernetnetwork device 220 may negotiate a transfer rate for the third link 219that is less than 1 Gbit/s and, as a result, data may be transferredover the second virtual channel 228 at a rate that exceeds the maximumbandwidth of the third link 219.

Systems and methods according to this disclosure address the foregoingissue by facilitating dynamic modification of the maximum transfer ratefor individual virtual channels of the first data link 209. To do so, atransfer rate for a virtual channel is compared to a correspondingdownstream transfer rate. To the extent the virtual channel transferrate exceeds the downstream transfer rate, a configuration message isgenerated and transmitted to an endpoint device. The configurationmessage automatically reconfigures the endpoint device to limit thetransfer rate over the virtual channel to the downstream transfer rate.When received, the configuration message automatically reconfigures theendpoint device to limit the transfer rate over the virtual channel tothe downstream rate. This process may be repeated for each virtualchannel of the endpoint device, thereby limiting data transferred overeach virtual channel to the maximum rate that may be transmitted along arespective path.

Referring to FIG. 2, for example, following negotiation of a totaltransfer rate for the first link 209 between the first Ethernet endpointdevice 208 and the first SONET endpoint device 210, downstream transferrates for each of the first path 222 and the second path 224 may bedetermined. As previously discussed in the context of FIG. 1,determining a downstream transfer rate may include, without limitation,one or more of retrieving internal configuration data from the firstSONET endpoint device 210, receiving a message from a downstream device(e.g., the second SONET endpoint device 210 for the first path 222 andthe third SONET endpoint device 220 for the second path 224) including adownstream transfer rate, and receiving a message including a downstreamtransfer rate from a computing device (not shown) communicativelycoupled to the SONET network 204 and a data source including informationregarding services provisioned over the SONET network 204.

Upon receiving downstream transfer rates corresponding to the first path222 and the second path 224, each downstream transfer rate is comparedto the negotiated transfer rate for transmitting data over the link 209.If the negotiated transfer rate exceeds one of the downstream transferrates, a configuration message is generated and sent to the firstEthernet endpoint device 208 that then causes the first Ethernetendpoint device 208 to restrict data transfer over the correspondingchannel to the downstream transfer rate. In one implementation, oneconfiguration message may be sent that causes all necessaryreconfiguration of the first Ethernet endpoint device 208.Alternatively, multiple configuration messages may be sent, each messagecorresponding to a subset of the paths for which limiting of acorresponding virtual channel is required. Although, a separate datatransfer rate is identified and implemented for each virtual channel ofthe first link 209, in alternative embodiments some or all virtualchannels may be limited to a particular downstream transfer rate. Forexample, all virtual channels may be limited to the lowest downstreamtransfer rate.

Similar to the example of FIG. 1, analysis of transfer rates andconfiguration of the first Ethernet endpoint device 208 and, morespecifically, the sub-interfaces of the first Ethernet endpoint device208 may occur at various times and in response to various events. Forexample, in certain implementations, the process of analyzing transferrates and reconfiguring the first Ethernet endpoint device 208 may occurin response to connecting and activating the first Ethernet endpointdevice 208 and the first SONET endpoint device 210. In anotherimplementation, the process may occur in response to a change in one ormore downstream networks that result in a change in one or moredownstream transfer rates. Such changes may include, without limitation,changes in the SONET network 204 (such as, without limitation, a channelof the SONET network 204 becoming impaired or being reactivatedfollowing repair) or changes to any downstream endpoint devices. In yetanother implementation, the process may occur in response to activatinga new data service or modifying an existing service provisioned over theSONET network 204. Similarly, the process may occur in response toactivation, deactivation, or other modification of a virtual channel ofthe first link 209.

FIG. 3 is an example of an enhanced autonegotiation method 300 inaccordance with this disclosure. With reference to the networkenvironment 100 of FIG. 1, the method includes initiating a connectionbetween a first endpoint device and a second endpoint device (operation302), each endpoint device corresponding to an endpoint of a network orsubnetwork between which data is to be exchanged. In the networkenvironment 100, for example, the first endpoint device may correspondto the first Ethernet endpoint device 108 and the second endpoint devicemay correspond to the first SONET endpoint device 110.

Once connected, a negotiation process may occur in which a transfer ratebetween the first and second endpoint devices is determined (operation304). In certain implementations, the negotiation process includes theendpoint devices 108, 110 exchanging a list of supported transmissionparameters. Such transmission parameters generally include transmissionspeed, but may further include, among other things, whether the devicesupports half or full duplex and specific flow control parametersimplemented by the device. Based on the exchanged transmissionparameters, a negotiated transfer rate is selected, which may generallybe the highest mutually supported transfer rate between the two devices,irrespective of any downstream bottlenecks. In FIG. 1, for example, thenegotiated transfer rate may be the maximum transfer rate between thefirst Ethernet endpoint device 108 and the first SONET endpoint device110 over the first link 109.

After negotiating the rate between the first and second endpoint, adownstream transfer rate is determined (operation 306). In certainimplementations, the downstream transfer rate corresponds to the lowesttransfer rate (i.e., a bottleneck) of a path along which data is to betransmitted. In certain implementations, the downstream transfer ratemay correspond to a transfer rate of a service provisioned over thenetwork associated with the second endpoint device. In FIG. 1, forexample, the downstream transfer rate may correspond to a provisionedtransfer rate for a data transfer service over the SONET network 104.The second transfer rate may also be a modified version of theprovisioned rate, such as in the event of a failure of one or more datapaths of the SONET network 104 or a reconstitution of previously faileddata paths. In another implementation, the second transfer rate maycorrespond to a transfer rate between destination endpoint devices. Forexample, a second SONET endpoint device 112 may negotiate a transferrate with a second Ethernet endpoint device 114 of a second Ethernetnetwork 106 configured to receive traffic from the first Ethernetnetwork 102.

The process of determining the downstream transfer rate may befacilitated, in certain implementations, by a computing devicecommunicatively coupled to the second network. For example, the networkenvironment 100 includes a computing device 120 communicatively coupledto the SONET network 104. The computing device 120 may be incommunication with a data source 122 that stores information, such astransfer rates of provisioned services, which may be used by thecomputing device 120 in determining the downstream transfer rate. Forexample, in certain implementations, the computing device 120 receives anotification from the first SONET endpoint device 110 followingcompletion of negotiation with the first Ethernet endpoint device 108,the message including, among other things, the negotiated rate. Themessage may further include an address or other identifier from which aparticular provisioned service may be identified. The computing device120 may then perform a lookup in the data source 122 using theidentifier to determine the transfer rate associated with theprovisioned service.

Once each of the negotiated and downstream rates is identified, the tworates are compared to determine whether the downstream rate is lowerthan the negotiated rate (operation 308). If so, a configuration messageis generated (operation 310) and transmitted to the first endpointdevice (operation 312). The configuration message may be generated by,among other devices, one or more of the first SONET endpoint device 110and the computing device 120. The configuration message generallyincludes instructions and related data that cause the first endpointdevice to update internal configuration data, limiting data transferfrom the first endpoint device to no more than the downstream transferrate. For example, in certain implementations, the configuration messageincludes a script or similar instructions that, when executed by thefirst endpoint device cause the first endpoint device to automaticallyactivate or modify buffers, traffic/rate shaping protocols, or othertransfer rate control mechanisms of the first endpoint device.

After reconfiguration of the first endpoint device (or if no suchreconfiguration was required), an operational loop may be executed inwhich the system is monitored for changes in the downstream rate. Whensuch a change is identified (operation 314), an update routine may beexecuted. A change in the downstream rate may occur in response tovarious events including, without limitation, installation of newdownstream equipment, modification of existing downstream equipment,provisioning of a new service, modification of an existing service,failure of downstream equipment or data transmission lines, and repairor reactivation of failed downstream equipment or data transmissionlines. Such events may raise an alert or otherwise trigger an exchangeof messages across a network or initiation of an autonegotiation processbetween devices of the network. For example, one or more devices coupledto a failed component may be configured to generate a message that isthen transmitted to the computing device 120 for subsequent handling.

When the downstream rate changes, the new downstream rate may becompared to the negotiated rate (operation 316) and, if the newdownstream rate is below the negotiated rate, the process of generatingand transmitting a configuration message (i.e., operations 310, 312) isexecuted to set the transfer rate of the first endpoint device to thenew downstream rate. If, on the other hand, the new downstream rate isnot less than the negotiated rate, a supplemental check to see if thecurrent transfer rate is equal to the negotiated rate may be performed(operation 318). If the current transfer rate is already the negotiatedrate (which generally corresponds to the maximum rate at which data canbe transferred over the first link 109), the system may return towaiting until a change in the downstream rate occurs. Otherwise, aconfiguration message for changing the transfer rate to the negotiatedrate may be generated and transmitted to the first endpoint device(operations 320 and 322). The system may then wait for subsequentchanges to the downstream transfer rate.

Although the method 300 illustrated in FIG. 3 is described primarily inthe context of the network environment 100 of FIG. 1, such a method maybe modified for application in an environment in which data is to betransmitted over multiple paths, such as the network environment 200 ofFIG. 2. For example, operations 306-322, which are directed to thegeneral process of identifying and remedying discrepancies betweendownstream transfer rates and a negotiated rate, may be conducted foreach service path (such as paths 222 and 224) extending from the secondendpoint device 210.

Referring to FIG. 4, a schematic illustration of an example computingsystem 400 having one or more computing units that may implement varioussystems and methods discussed herein is provided. It will be appreciatedthat specific implementations of these devices may be of differingpossible specific computing architectures not all of which arespecifically discussed herein but will be understood by those ofordinary skill in the art.

The computer system 400 may be a computing system capable of executing acomputer program product to execute a computer process. Data and programfiles may be input to computer system 400, which reads the files andexecutes the programs therein. Some of the elements of the computersystem 400 are shown in FIG. 4, including one or more hardwareprocessors 402, one or more data storage devices 404, one or more memorydevices 408, and/or one or more ports 408-412. Additionally, otherelements that will be recognized by those skilled in the art may beincluded in the computing system 400 but are not explicitly depicted inFIG. 4 or discussed further herein. Various elements of the computersystem 400 may communicate with one another by way of one or morecommunication buses, point-to-point communication paths, or othercommunication means not explicitly depicted in FIG. 4.

The processor 402 may include, for example, a central processing unit(CPU), a microprocessor, a microcontroller, a digital signal processor(DSP), and/or one or more internal levels of cache. There may be one ormore processors 402, such that the processor 402 comprises a singlecentral-processing unit, or a plurality of processing units capable ofexecuting instructions and performing operations in parallel with eachother, commonly referred to as a parallel processing environment.

The computer system 400 may be a conventional computer, a distributedcomputer, or any other type of computer, such as one or more externalcomputers made available via a cloud computing architecture. Thepresently described technology is optionally implemented in softwarestored on data storage device(s) 404, stored on memory device(s) 406,and/or communicated via one or more of the ports 408-412, therebytransforming the computer system 400 in FIG. 4 to a special purposemachine for implementing the operations described herein. Examples ofthe computer system 400 include personal computers, terminals,workstations, mobile phones, tablets, laptops, personal computers,multimedia consoles, gaming consoles, set top boxes, and the like.

One or more data storage devices 404 may include any non-volatile datastorage device capable of storing data generated or employed within thecomputing system 400, such as computer executable instructions forperforming a computer process, which may include instructions of bothapplication programs and an operating system (OS) that manages thevarious components of the computing system 400. Data storage devices 404may include, without limitation, magnetic disk drives, optical diskdrives, solid state drives (SSDs), flash drives, and the like. Datastorage devices 404 may include removable data storage media,non-removable data storage media, and/or external storage devices madeavailable via a wired or wireless network architecture with suchcomputer program products, including one or more database managementproducts, web server products, application server products, and/or otheradditional software components. Examples of removable data storage mediainclude Compact Disc Read-Only Memory (CD-ROM), Digital Versatile DiscRead-Only Memory (DVD-ROM), magneto-optical disks, flash drives, and thelike. Examples of non-removable data storage media include internalmagnetic hard disks, SSDs, and the like. One or more memory devices 406may include volatile memory (e.g., dynamic random access memory (DRAM),static random access memory (SRAM), etc.) and/or non-volatile memory(e.g., read-only memory (ROM), flash memory, etc.).

Computer program products containing mechanisms to effectuate thesystems and methods in accordance with the presently describedtechnology may reside in the data storage devices 404 and/or the memorydevices 406, which may be referred to as machine-readable media. It willbe appreciated that machine-readable media may include any tangiblenon-transitory medium that is capable of storing or encodinginstructions to perform any one or more of the operations of the presentdisclosure for execution by a machine or that is capable of storing orencoding data structures and/or modules utilized by or associated withsuch instructions. Machine-readable media may include a single medium ormultiple media (e.g., a centralized or distributed database, and/orassociated caches and servers) that store the one or more executableinstructions or data structures.

In some implementations, the computer system 400 includes one or moreports, such as an input/output (I/O) port 408, a communication port 410,and a sub-systems port 412, for communicating with other computing,network, or vehicle devices. It will be appreciated that the ports408-412 may be combined or separate and that more or fewer ports may beincluded in the computer system 400.

The I/O port 408 may be connected to an I/O device, or other device, bywhich information is input to or output from the computing system 400.Such I/O devices may include, without limitation, one or more inputdevices, output devices, and/or environment transducer devices.

In one implementation, the input devices convert a human-generatedsignal, such as, human voice, physical movement, physical touch orpressure, and/or the like, into electrical signals as input data intothe computing system 400 via the I/O port 408. Similarly, the outputdevices may convert electrical signals received from the computingsystem 400 via the I/O port 408 into signals that may be sensed asoutput by a human, such as sound, light, and/or touch. The input devicemay be an alphanumeric input device, including alphanumeric and otherkeys for communicating information and/or command selections to theprocessor 402 via the I/O port 408. The input device may be another typeof user input device including, but not limited to: direction andselection control devices, such as a mouse, a trackball, cursordirection keys, a joystick, and/or a wheel; one or more sensors, such asa camera, a microphone, a positional sensor, an orientation sensor, agravitational sensor, an inertial sensor, and/or an accelerometer;and/or a touch-sensitive display screen (“touchscreen”). The outputdevices may include, without limitation, a display, a touchscreen, aspeaker, a tactile and/or haptic output device, and/or the like. In someimplementations, the input device and the output device may be the samedevice, for example, in the case of a touchscreen.

The environment transducer devices convert one form of energy or signalinto another for input into or output from the computing system 400 viathe I/O port 408. For example, an electrical signal generated within thecomputing system 400 may be converted to another type of signal, and/orvice-versa. In one implementation, the environment transducer devicessense characteristics or aspects of an environment local to or remotefrom the computing device 400, such as, light, sound, temperature,pressure, magnetic field, electric field, chemical properties, physicalmovement, orientation, acceleration, gravity, and/or the like. Further,the environment transducer devices may generate signals to impose someeffect on the environment either local to or remote from the example thecomputing device 400, such as, physical movement of some object (e.g., amechanical actuator), heating or cooling of a substance, adding achemical substance, and/or the like.

In one implementation, a communication port 410 is connected to anetwork by way of which the computer system 400 may receive network datauseful in executing the methods and systems set out herein as well astransmitting information and network configuration changes determinedthereby. Stated differently, the communication port 410 connects thecomputer system 400 to one or more communication interface devicesconfigured to transmit and/or receive information between the computingsystem 400 and other devices by way of one or more wired or wirelesscommunication networks or connections. Examples of such networks orconnections include, without limitation, Universal Serial Bus (USB),Ethernet, Bluetooth®, Near Field Communication (NFC), Long-TermEvolution (LTE), and so on. One or more such communication interfacedevices may be utilized via communication port 410 to communicate one ormore other machines, either directly over a point-to-point communicationpath, over a wide area network (WAN) (e.g., the Internet), over a localarea network (LAN), over a cellular (e.g., third generation (3G) orfourth generation (4G)) network, or over another communication means.Further, the communication port 410 may communicate with an antenna forelectromagnetic signal transmission and/or reception.

The system set forth in FIG. 4 is but one possible example of a computersystem that may employ or be configured in accordance with aspects ofthe present disclosure. It will be appreciated that other non-transitorytangible computer-readable storage media storing computer-executableinstructions for implementing the presently disclosed technology on acomputing system may be utilized.

In the present disclosure, the methods disclosed may be implemented assets of instructions or software readable by a device. Further, it isunderstood that the specific order or hierarchy of steps in the methodsdisclosed are instances of example approaches. Based upon designpreferences, it is understood that the specific order or hierarchy ofsteps in the method can be rearranged while remaining within thedisclosed subject matter. The accompanying method claims presentelements of the various steps in a sample order and are not necessarilymeant to be limited to the specific order or hierarchy presented.

The described disclosure may be provided as a computer program product,or software, that may include a non-transitory machine-readable mediumhaving stored thereon instructions, which may be used to program acomputer system (or other electronic devices) to perform a processaccording to the present disclosure. A machine-readable medium includesany mechanism for storing information in a form (e.g., software,processing application) readable by a machine (e.g., a computer). Themachine-readable medium may include, but is not limited to, magneticstorage medium, optical storage medium; magneto-optical storage medium,read only memory (ROM); random access memory (RAM); erasableprogrammable memory (e.g., EPROM and EEPROM); flash memory; or othertypes of medium suitable for storing electronic instructions.

While the present disclosure has been described with reference tovarious implementations, it will be understood that theseimplementations are illustrative and that the scope of the presentdisclosure is not limited to them. Many variations, modifications,additions, and improvements are possible. More generally, embodiments inaccordance with the present disclosure have been described in thecontext of particular implementations. Functionality may be separated orcombined in blocks differently in various embodiments of the disclosureor described with different terminology. These and other variations,modifications, additions, and improvements may fall within the scope ofthe disclosure as defined in the claims that follow.

It should be understood from the foregoing that, while particularembodiments have been illustrated and described, various modificationscan be made thereto without departing from the spirit and scope of theinvention as will be apparent to those skilled in the art. Such changesand modifications are within the scope and teachings of this inventionas defined in the claims appended thereto.

We claim:
 1. A method of establishing a data transfer rate betweennetwork endpoints, the method comprising: initiating a connectionbetween a first endpoint of a first network and a second endpoint of asecond network, wherein the connection between the endpoint of the firstnetwork and the endpoint of the second network can transfer data at upto a first transfer rate; determining the first transfer rate is greaterthan a second transfer rate for transferring data over the secondnetwork; and transmitting, in response to determining the first transferrate is greater than the second transfer rate, a configuration messageto a network device corresponding to the first endpoint, wherein theconfiguration message causes the network device to limit transfer ofdata over the connection from the first endpoint to the second endpointto no greater than the second transfer rate.
 2. The method of claim 1,wherein the first network is an Ethernet network and the second networkis a synchronous optical networking (SONET) network.
 3. The method ofclaim 1, wherein the second transfer rate is a transfer rate between thesecond endpoint and a third endpoint of a third network.
 4. The methodof claim 1, wherein the step of determining the first rate is greaterthan the second transfer rate occurs in response to identifying adecrease in throughput along a communication path between the secondendpoint and a third endpoint of the second network.
 5. The method ofclaim 4, further comprising: identifying an increase in the throughputalong the communication path between the second endpoint and the thirdendpoint; and transmitting a second configuration message to the networkdevice, wherein the second configuration message causes the networkdevice to limit transfer of data from the first endpoint to the secondendpoint to a third transfer rate, the third transfer rate up to andincluding the first transfer rate.
 6. The method of claim 1, wherein thesecond network includes one or more third endpoints connected to arespective sub-interface of the second endpoint and enabling arespective transfer rate therebetween, and the second transfer rate is asum of the respective transfer rates between the second endpoint and theone or more third endpoints.
 7. The method of claim 6, wherein thetransfer rate between each sub-interface of the second endpoint and arespective third endpoint is limited to the lowest transfer rate betweenany sub-interface of the second endpoint and its corresponding one ofthe third endpoints.
 8. The method of claim 6, wherein the connectionbetween the first endpoint and the second endpoint includes a pluralityof virtual channels, each virtual channel corresponding to a pathbetween one of the sub-interfaces of the second endpoint and arespective one of the third endpoints, and the configuration messagecauses the network device to limit data transfer for each virtualchannel to the transfer rate between the one of the sub-interfaces andthe one of the third endpoints corresponding to the virtual channel. 9.The method of claim 1, wherein the second transfer rate is obtained froma concatenator adapted to aggregate a plurality of links of the secondnetwork, and the second transfer rate is a combined transfer rate of theaggregated links.
 10. A system for controlling data transfer ratesbetween network devices, the system comprising: a computing devicecomprising a processor and one or more non-transitory tangiblecomputer-readable storage media storing computer-executable instructionsthat, when executed by the processor, cause the computing device to:determine that a negotiated transfer rate for transferring data from afirst network device to a second network device over a first networkexceeds a downstream transfer rate, the downstream transfer ratecorresponding to a transfer rate between the second network device and athird network device over a second network; generate a configurationmessage that, when received by the first network device, causes thefirst network device to limit data transfer between the first networkdevice and the second network device to no greater than the downstreamtransfer rate; and transmit the configuration message to the firstnetwork device.
 11. The system of claim 10, wherein the first networkdevice is an Ethernet network and the second network is a synchronousoptical networking (SONET) network.
 12. The system of claim 10, whereinthe downstream transfer rate is based on a provisioned transfer rateover a network path between the second network device and the thirdnetwork device.
 13. The system of claim 10, wherein the downstreamtransfer rate is a second negotiated transfer rate between the thirdnetwork device and a fourth network device.
 14. The system of claim 10,wherein the data transfer between the first network device and thesecond network device occurs over a link with a plurality of virtualchannels for communicating data between the first network device and thesecond network device.
 15. The system of claim 10, wherein theinstructions further cause the computing device to: identify a change inthe downstream transfer rate resulting in a first modified downstreamtransfer rate different from the downstream transfer rate; determine thefirst modified downstream transfer rate is less than the negotiatedrate; generate a second configuration message that, when received by thefirst network device, causes the first network device to limit datatransfer between the first network device and the second network deviceto no greater than the first modified downstream transfer rate; andtransmit the second configuration message to the first network device.16. The system of claim 15, wherein the instructions further cause thecomputing device to: identify a second change in the downstream transferrate resulting in a second modified downstream transfer rate differentthan the first modified downstream transfer rate; determine the secondmodified downstream transfer rate is greater than the first modifieddownstream transfer rate; generate a third configuration message that,when received by the first network device, causes the first networkdevice to increase data transfer between the first network device andthe second network device to the lesser of the second modifieddownstream transfer rate and the negotiated transfer rate; and transmitthe third configuration message to the first network device.
 17. Thesystem of claim 10, wherein the downstream transfer rate is a sum oftransfer rates between the second network device and a plurality ofthird network devices, the first network device transferring data toeach of the plurality of third network devices over respective virtualchannels.
 18. The system of claim 17, wherein the configuration messagelimits data transfer over each of the virtual channels to the lowesttransfer rate of the transfer rates between the second network deviceand each of the plurality of third network devices.
 19. A non-transitorycomputer readable medium storing instructions that, when executed by oneor more processors of a computing device, cause the computing device to:determine that a negotiated transfer rate for transferring data from afirst network device to a second network device over a first networkexceeds a downstream transfer rate, the downstream transfer ratecorresponding to a transfer rate between the second network device and athird network device over a second network; generate a configurationmessage that, when received by the first network device, causes thefirst network device to limit data transfer between the first networkdevice and the second network device to no greater than the downstreamtransfer rate; and transmit the configuration message to the firstnetwork device.
 20. The non-transitory computer readable medium of claim19, wherein the instructions further cause the computing device to:identify a change in the downstream transfer rate resulting in amodified downstream transfer rate different than the downstream transferrate; generate a configuration message that, when received by the firstnetwork device, causes the first network device to change a rate of datatransfer between the first network device and the second network device;and transmit the configuration message to the first network device,wherein, if the modified downstream transfer rate is less than thedownstream transfer rate, the rate of data transfer is changed to a rateequal to or below the modified downstream transfer rate, and, if themodified downstream transfer rate is greater than the downstreamtransfer rate, the rate of data transfer is changed to a rate that isthe lesser of the modified downstream transfer rate and the negotiatedtransfer rate.